Satellite communication network terminal installation method and system

ABSTRACT

A method and system for installing a terrestrial antenna for a satellite communication network. In the system and method, a remote unit is provided to an installation location for the terrestrial antenna. The remote unit is configured to communicate with a satellite of the satellite communication network and includes a memory in which is stored antenna information pertaining to positioning of the terrestrial antenna with respect to a virtual beam generated by the satellite. The information is accessible by a code. Thus, the antenna information is access from the memory at the installation location using the code, and the terrestrial antenna in relation to a virtual beam generated by the satellite based on the antenna information accessed from the memory at the installation location.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Divisional of U.S. patent application Ser. No.15/281,845, filed Sep. 30, 2016, the content of which is herebyincorporated herein by reference.

BACKGROUND Field of the Invention

The present invention generally relates to a satellite communicationterminal installation method and system. More particularly, the presentinvention relates to a system and method for installing a satellitecommunication terminal at an end-user site without the need to obtainlocation information, such as GPS information, at the end-user site.

Background Information

Communication networks, such as satellite communication networks, employsatellite communication terminals at end-user sites which communicatewith one or more satellites in the satellite communication network. Asunderstood in the art, each satellite in the satellite communicationnetwork propagates at least one user beam onto a specific region of theearth. Also, each user beam typically includes a plurality of smallersized virtual beams within the user beam. A satellite terminal includesa dish which, during installation, is pointed in the appropriatedirection so that a virtual beam within the user beam is able to provideterminal location information which is accurate enough for the satelliteterminal to close a link with the satellite as long as the satelliteterminal is within the virtual beam coverage area as understood in theart. As also understood in the art, the size of the virtual beam (e.g.,the number of the virtual beams in a user beam) will be determined bythe timing error that is permissible in the system, which can be drivenby, for example, customers' requirements as well as the link budgetcalculation.

In order to select an appropriate virtual beam, it is necessary for thespecific location (i.e., longitude and latitude) of the satelliteterminal to be known. When ordering an installation, a customer providesthe installation location which can be as specific as the street addressor even the GPS location information, or can be as general as simply thecity or town name, or the postal code. Thus, in a typical installationprocess, the installer at the end-user site can use a locationdetermining device, such as a global positioning system (GPS) device,Google Maps and so on, to determine the location of the satelliteterminal if the customer only provided a street address or generalinformation such as city and/or postal code. However, this process ofobtaining location information complicates the overall installationprocess, and thus makes the installation process more time consuming.Furthermore, it is possible that in certain remote locations, suchlocation information is difficult to obtain or unobtainable, whichfurther complicates the process.

SUMMARY

In order to address these issues, the disclosed embodiments provide amethod and system for installing a terrestrial antenna for a satellitecommunication network. In the system and method, a remote unit isprovided to an installation location for the terrestrial antenna. Theremote unit is configured to communicate with a satellite of thesatellite communication network, and includes a memory in which isstored antenna information pertaining to positioning of the terrestrialantenna with respect to a virtual beam generated by the satellite. Theinformation is accessible by a code. Thus, the antenna information isaccessed from the memory at the installation location using the code,and the terrestrial antenna is positioned in relation to a virtual beamgenerated by the satellite based on the antenna information accessedfrom the memory at the installation location.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the attached drawings which form a part of thisoriginal disclosure:

FIG. 1 illustrates an example of a satellite communication networkaccording to a disclosed embodiment;

FIG. 2 is a conceptual flow diagram illustrating an example ofoperations associated with a terminal installation process according toa disclosed embodiment;

FIG. 3 is a flow chart illustrating an example of operations performedduring the equipment manufacturing phase shown in FIG. 2;

FIG. 4 illustrates an example of a user beam generated by a satellite inthe satellite communication network shown in FIG. 1;

FIG. 5 illustrates an example of virtual beams included in a user beamsuch as that shown in FIG. 4;

FIG. 6 is a conceptual block diagram illustrating an example of asatellite broadcast communication configuration file created during theequipment manufacturing phase shown in FIG. 2;

FIG. 7 is a flow chart illustrating an example of operations performedduring the business support system phase and the on-site terminalinstallation phase shown in FIG. 2;

FIG. 8 is an exemplary flow diagram illustrating an example ofoperations performed during the business support system phase and theon-site terminal installation phase shown in FIGS. 2 and 7;

FIG. 9 illustrates an example of a display screen for enteringinformation during the on-site terminal installation phase as shown inFIGS. 2, 7 and 8; and

FIG. 10 illustrates an example of a display screen displaying testinginformation during testing operations performed in the on-site terminalinstallation phase as shown in FIGS. 2, 7 and 8.

DETAILED DESCRIPTION OF EMBODIMENTS

Selected embodiments will now be explained with reference to thedrawings. It will be apparent to those skilled in the art from thisdisclosure that the following descriptions of the embodiments areprovided for illustration only and not for the purpose of limiting theinvention as defined by the appended claims and their equivalents.

FIG. 1 illustrates an example of a satellite communication network 10according to an exemplary embodiment. A satellite communication network10 typically includes a plurality of terrestrially mounted gateways 12that communicate with one or more orbiting satellites 14. Each satellitegateway includes an antenna dish 16, a transceiver 18, a controller 20,a memory 22 and other types of equipment (not shown) such as amplifiers,waveguides and so on as understood in the art on which enablecommunication between the gateway 12 and a plurality of satellite userterminals 24 via one or more of the orbiting satellites 14. The memory22 can be, for example, an internal memory in the gateway 12, or othertype of memory devices such as flash memory or hard drives with externalhigh speed interface such as a USB bus or an SATA bus, or remotememories such as cloud storage and so on. These other types of memorycan be present at the gateway 12 or accessible at a location apart fromthe gateway 12 via a network connection such as an Ethernet connection,a WiFi connection or any other suitable type of connection as understoodin the art.

As understood in the art, the controller 20 preferably includes amicrocomputer with a control program that controls the gateway 12 asdiscussed herein. The controller 20 can also include other conventionalcomponents such as an input interface circuit, an output interfacecircuit, and storage devices such as a ROM (Read Only Memory) device anda RAM (Random Access Memory) device. The RAM and ROM store processingresults and control programs that are run by the controller 20. Thecontroller 20 is operatively coupled to the components of the gateway 12as appropriate, in a conventional manner. It will be apparent to thoseskilled in the art from this disclosure that the precise structure andalgorithms for the controller 20 can be any combination of hardware andsoftware that will carry out the functions of the present invention.

The gateway 12, satellites 14 and satellite user terminals 24 typicallycommunicate with each other over a radio frequency link, such as aKu-band link, a Ka-band link or any other suitable type of link asunderstood in the art. Also, one or more of the gateways 12 can beconfigured as a network management center or network operating centerwhich, among other things, operate to communicate with remote sites,such as web content providers 26, via the Internet 28, cloud storage, orother communication networks as understood in the art. In addition, thegateways 12 can communicate with each other via, for example, theInternet 28 or other communication networks.

As further shown in FIG. 1, a satellite user terminal 24 typicallyincludes an antenna dish 30 that is commonly referred to as an outdoorunit (ODU), and a device such as a set-top box or other type ofequipment that is commonly referred to as an indoor unit (IDU) 32. TheIDU 32 typically includes a transceiver 34, a controller 36, a memory38, a local server 40 and other types of equipment (not shown) such asamplifiers, waveguides and so on as understood in the art on whichenable communication between the satellite user terminal 24 and one ormore gateways 12 via one or more of the orbiting satellites 14. Atransceiver 34 can include, for example, an integrated satellite modemand any other suitable equipment which enables the transceiver 34 tocommunicate with one or more of the orbiting satellites 14 as understoodin the art. The memory 38 can be, for example, an internal memory in thesatellite user terminal 24, or other type of memory devices such as aflash memory or hard drives with external high speed interface such as aUSB bus or an SATA bus, or remote memories such as cloud storage and soon. These other types of memory can be present at the satellite userterminal 24 or accessible at a location apart from the satellite userterminal 24 via a network connection such as an Ethernet connection, aWiFi connection or any other suitable type of connection as understoodin the art.

As with the controller 20 for a gateway 12, the controller 36 preferablyincludes a microcomputer with a control program that controls thesatellite user terminal 24 as discussed herein. The controller 36 canalso include other conventional components such as an input interfacecircuit, an output interface circuit, and storage devices such as a ROM(Read Only Memory) device and a RAM (Random Access Memory) device. TheRAM and ROM store processing results and control programs that are runby the controller 36. The controller 36 is operatively coupled to thecomponents of the satellite user terminal 24 as appropriate, in aconventional manner. It will be apparent to those skilled in the artfrom this disclosure that the precise structure and algorithms for thecontroller 36 can be any combination of hardware and software that willcarry out the functions of the present invention.

The memory 38 can be, for example, an internal memory in the terminal24, or other type of memory devices such as a flash memory or harddrives with external high speed interface such as a USB bus or an SATAbus, or remote memories such as cloud storage and so on. These othertypes of memory can be present at the terminal 24 or accessible at alocation apart from the terminal 24 via a network connection such as anEthernet connection, a WiFi connection or any other suitable type ofconnection as understood in the art. Also, the local server 40 cancommunicate with an access point 42, such as a WAP or any other suitabledevice, which enables the local server 40 to provide packets to end userdevices 44 as discussed herein. Such end user devices 44 include, forexample, desktop computers, laptop or notebook computers, tablets (e.g.,iPads), smart phones, Smart TVs and any other suitable devices asunderstood in the art. Naturally, the communications between the localserver 38, the access point 42 and the end user devices 44 can occurover wireless connections, such as WiFi connections, as well as wiredconnections as understood in the art.

FIGS. 2-10 illustrate examples of operations and features associatedwith a user terminal installation process according to disclosedembodiments. In a typical installation process, the installer at theend-user site uses a location determining device, such as a GPS device,to determine the location of the satellite terminal. However, theinstallation process according to the disclosed embodiments provides anIDU 32 having a memory 38 into which has been stored satellite terminalinstallation data that is accessible by a code. As discussed in moredetail below, the stored satellite terminal installation data includes,among other things, a database of “spreadsheets” for all of the userbeams (UBs) and their respective virtual beams (VBs) generated by thesatellite communication network 10 in relation to correspondinglocations, such as latitude and longitude, on the surface of the earth.Thus, the database matches virtual beams to location data. That is,database matches each of the virtual beams to the respective latitudesand longitudes of coverage areas on the surface of the earth that areprovided by the respective virtual beams.

As can be appreciated from the exemplary flow diagram shown in FIG. 2and the flowchart of FIG. 3, the process according to a disclosedembodiment includes three phases, namely, the equipment manufacturingphase 100, the business support system phase 200 and the on-siteterminal installation phase 300. Each of these phases will now bedescribed.

During operation 101, information based on the network service provider(NSP) and the world wide (WW) virtual network operator (VNO) is capturedfor the satellite communication network 10 in any suitable manner asunderstood in the art. The information includes, for example,coordinates of the respective beam center and respective beam radii foreach user beam, along with the respective coverage areas for each NSPand WW VNO that are mapped to the user beams. The information furtherincludes information pertaining to a minimum number of virtual beams foreach user beam radii to provide precise enough location info in orderfor a terminal 24 to acquire access to the satellite communicationnetwork 10 via, for example, large aperture bootstrap aloha for rangingwhich can be based upon TDMA closed-loop timing analysis, or any othersuitable type of ranging, as understood in the art.

For example, as shown in FIG. 4, each user beam UB is typically shapedas an ellipse with a major axis and a minor axis of different lengths.The ellipses can also be rotated with respect to an X-Y coordinatesystem as understood in the art. Each user beam UB includes a set ofvirtual beams VB as shown, for example, in FIG. 5. A virtual beam canhave, for example, a radius that is small enough to acquire an alohaTDMA timeslot of 1 msec size, or any other suitable size as understoodin the art. A union of the virtual beams VB of a user beam UB define thecoverage area for a single user beam UB. The user beams UB and theirrespective virtual beams VB can be arranged in a best fit manner toprovide a coverage area for the terminals 34 as understood in the art.

During operation 102, information pertaining to the configuration fortransmission for each IDU 32 in the satellite communication network 10is captured in any suitable manner as understood in the art.

During operation 103, the database including the spreadsheets for eachof the virtual beams captured during operations 101 and 102 as discussedabove is created. In this example, operation 103 includes threesub-operations 103-1, 103-2 and 103-3. During operation 103-1 a virtualbeam map is created for all of the virtual beams VBs. As part of thatvirtual beam map, during operation 103-2, a respective unique installcode for each virtual beam VB is entered in the respective spreadsheetfor each virtual beam VB. The spreadsheets can include or be associatedwith keyhole markup language (KML) files as understood in the art.

In the examples discussed herein, an install code is a three-charactercode. However, the install code can be of any suitable length orconfiguration in order to enable an installer to access the installationinformation as discussed herein. In the examples discussed herein, eachinstall code is a three-digit alpha numeric value. In order to avoidconfusion at the installation site by the installer, each install codeshould avoid the number 0, upper case letter O, and lower case letter osince they can be easily confused on a printed label. For similarreasons, each install code should also should avoid number 1, upper caseletter I, and lower case letter l since they can be easily confused on aprinted label. Likewise, each install code should avoid upper case Q andupper case O if upper case is used since they can be easily confused ona printed label. Furthermore, each install code should avoid specialcharacters (non-alpha, non-numeric) for ease of entry by the installer,and should avoid lower case characters and only use upper casecharacters to avoid incorrect data entry by the installer.

Table 1 below is an example of three-character install codes associatedwith the virtual beams shown in FIG. 5.

TABLE 1 Parent Beam Virtual_Beam_ID Location Install_Code 20.1 KinshasaA55 20.2 Kinshasa KFS 20.3 Kinshasa 5CT 20.4 Kinshasa 739 20.5 KinshasaMK6 20.6 Kinshasa 3FR 20.7 Kinshasa YCR 20.8 Kinshasa FL5 20.9 KinshasaWBZ 20.11 Kinshasa VZA 20.12 Kinshasa U79 20.13 Kinshasa 4ML 20.14Kinshasa JWR 20.15 Kinshasa F45 20.16 Kinshasa 2R4 20.17 Kinshasa BPH20.18 Kinshasa DJX 20.19 Kinshasa TJP

The respective virtual beam spreadsheet for each respective virtual beamcan include other information such as the virtual beam id, parent beamid, virtual beam center azimuth, virtual beam center elevation, beamradius, beam owner, parent beam state, virtual beam state, parent beamlocation, beam type and so on. This information matches the sbc.cfg file(satellite broadcast communication configuration file) that is createdduring operation 103-1.

As shown in FIG. 6, the sbc.cfg files include information pertaining tothe network service provider, the satellites 14 in the satellitecommunication network 10, the domain name system (DNS) and timers, theoutdoor units (ODU) and their types of hardware such as antenna size(e.g., a 74 cm antenna, a 98 cm antenna or a 120 cm antenna), RF power(e.g., 1 Watt RF or 2 Watt RF) and so on. The sbc.cfg can furtherinclude information pertaining to the user beams UBs, the virtual beamsVBs and their outroutes, and the selection weights associated with thevirtual beams as understood in the art.

During operation 104, the information created and generated duringoperation 103, including the information for the spreadsheets for eachof the virtual beams captured during operations 101 and 102, is storedin the memory 38 of each of the IDUs 32. Operation 104 can includeoperation 104-1 during which the IDU 32 is manufactured, and operation104-2 in which the sbc.cfg files and any of the other informationcreated and generated during operation 103 are stored in the memory 38of each of the IDUs 32. Thus, data pertaining to all of the virtualbeams VB and all of the install codes are stored in the memory 38 ofeach of the IDUs 32. Each IDU 32 is assigned a different part number tocreate WW VNO custom branded IDUs 32. Optionally, factory acceptancetesting can be performed on each of the IDUs 32 in operation 105. TheIDUs 32 are then ready for deployment to end users during the serviceoperation 106 on as as-needed basis.

Exemplary operations of the business support system phase 200 are shownin FIGS. 2, 7 and 8, when an end-user wishes to obtain service from thesatellite communication network 100, the end-user contacts the businesssupport system in step 201 to request installation of a terminal 24. Anoperator (the BSS operator) at the business support system can take theend-user's information via telephone, on-line or in any suitable manner.The end-user's information includes the address at which the terminal 24is to be installed (the installation address), which can correspond tothe end-user's address.

During step 202, the BSS operator converts the installation address intolongitude and latitude coordinates using, for example, Google Maps,Google Earth or any other suitable software or application. For example,the BSS operator can us the Google Map API to convert the street addressof the installation address into latitude and longitude. The BSSoperator can also use the Google Earth GUI to locate the street addressto determine its latitude and longitude, or some similar map applicationthat provides latitude and longitude as understood in the art. Inaddition, the BSS operator can update the information stored in thememory 38 of a terminal 24, such as information pertaining to additionaluser beams and virtual beams in additional service areas, and so on asunderstood in the art.

In step 203, the BSS operator determines whether a terminal 24 can bedeployed and will operate at the installation address. For instance, theBSS Operator enters the selected NSP or WW VNO into a database ofvirtual beams to filter the list of available virtual beams at thatinstallation address. If the BSS operator determines in step 204 thatthe installation address fails to lie within any of the user beams, thenservice is unavailable at that installation address. In this case, theBSS operator informs the end-user that service is not available in step205. However, if service is available at the installation address, theBSS operator will create a service order in step 206.

To create the service order, the BSS operator can use, for example, anNMS-provided web-based API to convert the latitude and longitude into aselected VB and its install code. The BSS operator includes the installcode in the service order and provides this install code to the end-userand/or to the installer of the terminal 24 in any suitable manner.Naturally, the end-user can be the person who will install the terminal24. For instance, the BSS operator can provide the install code as aprinted code on the service order sent to the end-user or installer withthe terminal 24. The BSS operator can send the install code to the enduser and/or installer via email, via online access, via a text messageor voice message, or in any other suitable manner.

In step 207, the BSS operator creates a work order. In step 208, the BSSoperator has the terminal 24 delivered to the end-user, which could bethe installer, or to the installer.

Exemplary embodiments of the on-site terminal installation phase 300 areshown in FIGS. 2, 7 and 8. In step 301, the installer prepare theequipment of the terminal 24. In step 302, the installer installs theIDU 32 and powers up the IDU 32. The installer uses a user interface,such as any of the type of end user devices 44 discussed above, toaccess the installation information stored in the memory 38 of theterminal 24 as discussed above. In particular, in step 303, the useruses an end user device 44 to enter the install code. For example, asshown in FIG. 9, the end user device 44 can display a window W on itsgraphical user interface into which the installer can enter the installcode (e.g., ZZZ). If the install code is invalid or incorrectly entered,the end user device 44 can display an error message in the window W, andthe installer can try to reenter the code or contact the businesssupport system (BSS) if failures continue.

In response to a properly entered access code, the controller 36 accessthe installation information from the memory 38, and that informationis, for example, displayed on the end user device 44. Thus, thecontroller 36 of the terminal 24 converts the install code based upon,for example, its sbc.cfg into a selected virtual beam. The terminal 24informs the installer via the end user device 44 of the installationinformation for the dish 30, including azimuth, elevation, tilt,polarization for the selected virtual beam center, which is converted bythe terminal 24 into latitude and longitude used by the terminal as partof its terminal ranging, commissioning, registration, and swaps.

The installer uses this installation information to install the dish 30and angle the dish appropriately in steps 304, 305 and 306. For example,the installer can mount the dish in step 304. In step 305, the installercan install the interfacility link (IFL), such as the cable between theODU and the IDU. In step 306, the installer can point the dish 30 at theappropriate elevation and angle as understood in the art. The user canfollow the instruction indicated in the window W displayed by the enduser device 44 by clicking on the appropriate buttons (e.g., “next,”etc.) and dropdown menus.

Examples of the type of information that can be displayed are shown inTables 2 and 3 below. In Table 2, the Target and Estimated SQF valuesare displayed since the local on-site verification tool (OVT) isenabled. In Table 3, the Target and Estimated SQRF values are notdisplayed since the local OVT is disabled. Naturally, the amount ofinformation and the manner in which the information is displayed can beprogrammed into the terminal 24 during the equipment manufacturing phase100 as discussed above and/or during updating in the business supportsystem phase 200.

TABLE 2 Satellite Name EchoStar-19-NAD Azimuth 189.589° Elevation46.598° Antenna Tilt 8.026° Uplink Pol Right-Hand (RH) Beam Selected 14Outroute Num 16 Target SQF (System) 220 Estimated Target SQF (Local) 180

TABLE 3 Satellite Name EchoStar-19-NAD Azimuth 189.589° Elevation46.598° Antenna Tilt 8.026° Uplink Pol Right-Hand (RH) Beam Selected 14Outroute Num 16

In step 307, which is optional, the installer can perform verificationoperations as understood in the art. For example, the terminal 24 canacquire a system information message containing the required minimumsignal strength value for the given user beam's center. The terminal 24extrapolates its required signal strength value based upon its virtualbeam center's distance from the user beam's center. The installer canperforms antenna pointing operations either using a DAPT connectedinline of the IFL at the ODU which provides a good/bad indicator to theinstaller if the signal strength meets its required minimum, or using aWiFi enabled device with a web browser to connect via WiFi to reach theterminal IDU 32 which shows signal strength values on its Web UI withthe WiFi being provided by either a separate installer-provided WiFirouter with a wired connection to the terminal IDU 32 or an integratedWiFi router built into the terminal IDU 32. The installer performsantenna pointing to maximize the signal strength based upon this givenfeedback of signal strength values as they adjust the terminal antenna.

If the installation is unsuccessful, the installer can be instructed bythe information displayed by the end user device 44 to perform any orall of the operations 304, 305 and 306 again, and repeat the validationtesting in step 307. Once the testing is successful, the installerperforms registration operations in step 308 to register the terminal24. At the end of the terminal's registration, the terminal 24 providesits transmit and receive related EsNo readings, antenna size and radiowattage data to the test center, and based on the terminal's relativelocation to the center of the user beam, and the OVT test suitenormalizes the thresholds and values in a manner consistent with theresult of the calculation performed during the antenna pointing process.

The installer then activates the service in step 309. In addition, instep 310 which is optional, the installer may optionally perform, basedupon the business processes defined by the NSP, a centralized OVT inorder to get a signoff code for the installation. For instance, theinstaller can click on the URL link on the end user device 44 tonavigate to the centralized OVT's web page. The centralized OVT collectsactual install info from the terminal 24 to determine if theinstallation meets required value ranges for a successful install. Thecentralized OVT provides a sign off code to the installer for asuccessful install. While the testing is being performed, the GUI of theend user device 44 can display information pertaining to the testing asshown, for example, in FIG. 10. For instance, the installer can updatethe local OVT mandatory optional field by, for example, selecting adropdown menu. The terminal 24 can acquire this message and normalizethe downlink EsNo value to at least meet the minimum threshold to passthe antenna pointing process. Alternatively, the controller 36 in theterminal 24 can still calculate the normalized downlink EsNo value,whether the EsNo value meets the threshold value or not, the operatorcan always move to the next page of installation.

Once the installation and OVT operations are complete, the end-user canthen begin accessing the satellite communication network 10 in step 311to, for example, browse the Internet and so on.

As can be appreciated from the above, the method and system according tothe disclosed embodiments requires no use of GPS or any other locationdetermining services during the installation of the terminal 24. Theembodiments also improve the usability of the software in the terminal24 by reducing the number of parameters required during theinstallation, which in turn reduces the possibilities of satellite beaminfo selection error and terminal location errors caused by human error.Thus, the installation process is simplified since it is unnecessary fordetailed messages displayed on the graphical user interface of the enduser device 44 being used by the installer, and instead, more effectiveand detailed antenna pointing guidelines are displayed. Moreover, theembodiments are able to support GPS-less installation with a locationerror up to 40 KM. Each terminal will be assigned with a 3-digitalpha-numerical install code. Also introduced a new mechanism to providebetter antenna pointing guide lines during installation.

General Interpretation of Terms

In understanding the scope of the present invention, the term“comprising” and its derivatives, as used herein, are intended to beopen ended terms that specify the presence of the stated features,elements, components, groups, integers, and/or steps, but do not excludethe presence of other unstated features, elements, components, groups,integers and/or steps. The foregoing also applies to words havingsimilar meanings such as the terms, “including”, “having” and theirderivatives. Also, the terms “part,” “section,” “portion,” “member” or“element” when used in the singular can have the dual meaning of asingle part or a plurality of parts. Also, the term “detect” as usedherein to describe an operation or function carried out by a component,a section, a device or the like includes a component, a section, adevice or the like that does not require physical detection, but ratherincludes determining, measuring, modeling, predicting or computing orthe like to carry out the operation or function. The term “configured”as used herein to describe a component, section or part of a deviceincludes hardware and/or software that is constructed and/or programmedto carry out the desired function. The terms of degree such as“substantially”, “about” and “approximately” as used herein mean areasonable amount of deviation of the modified term such that the endresult is not significantly changed.

While only selected embodiments have been chosen to illustrate thepresent invention, it will be apparent to those skilled in the art fromthis disclosure that various changes and modifications can be madeherein without departing from the scope of the invention as defined inthe appended claims. For example, the size, shape, location ororientation of the various components can be changed as needed and/ordesired. Components that are shown directly connected or contacting eachother can have intermediate structures disposed between them. Thefunctions of one element can be performed by two, and vice versa. Thestructures and functions of one embodiment can be adopted in anotherembodiment. It is not necessary for all advantages to be present in aparticular embodiment at the same time. Every feature which is uniquefrom the prior art, alone or in combination with other features, alsoshould be considered a separate description of further inventions by theapplicant, including the structural and/or functional concepts embodiedby such feature(s). Thus, the foregoing descriptions of the embodimentsaccording to the present invention are provided for illustration only,and not for the purpose of limiting the invention as defined by theappended claims and their equivalents.

What is claimed is:
 1. A system for installing a terrestrial antenna fora satellite communication network, the system comprising: a remote unitcomprising a transceiver configured to communicate with a satellite ofthe satellite communication network, and a memory in which is storedantenna information pertaining to positioning of the terrestrial antennawith respect to a virtual beam generated by the satellite, the antennainformation being accessible by a code associated with the virtual beam.2. The system according to claim 1, further comprising a controller,configured to retrieve the antenna information from the memory inresponse to entry of the code by a user interface, and provide theantenna information to the user interface.
 3. The system according toclaim 1, wherein the memory stores a plurality of sets of antennainformation, each of the sets of antenna information being accessible bya respective code and including information pertaining to positioning ofthe terrestrial antenna with respect to a respective virtual beamgenerated by the satellite.
 4. The system according to claim 3, furthercomprising a controller, configured to select one of the sets of antennainformation from the memory in response to entry of the code by a userinterface, and provide the selected antenna information to the userinterface.
 5. The system according to claim 1, further comprising acontroller, configured to perform testing to verify accuracy of pointingof the terrestrial antenna with respect to the virtual beam.
 6. Thesystem according to claim 1, wherein the code includes a plurality ofcharacters and is identified in a communication to an end user orinstaller of the remote unit.
 7. The system according to claim 1,wherein the antenna information includes a virtual beam identificationrelating to the virtual beam.
 8. The system according to claim 1,wherein the antenna information includes a parent beam identificationrelating to the virtual beam.
 9. The system according to claim 1,wherein the antenna information includes a virtual beam azimuth relatingto the virtual beam.
 10. The system according to claim 1, wherein theantenna information includes a virtual beam elevation relating to thevirtual beam.
 11. The system according to claim 1, wherein the antennainformation includes a beam radius relating to the virtual beam.
 12. Thesystem according to claim 1, wherein the antenna information includes abeam owner relating to the virtual beam.
 13. The system according toclaim 1, wherein the antenna information includes a parent beam staterelating to the virtual beam.
 14. The system according to claim 1,wherein the antenna information includes a parent beam location relatingto the virtual beam.
 15. The system according to claim 1, wherein theantenna information includes a beam type relating to the virtual beam.16. The system according to claim 1, wherein the antenna informationincludes a selection weight relating to the virtual beam.
 17. The systemaccording to claim 1, wherein the antenna information includes anoutroute relating to the virtual beam.
 18. The system according to claim1, wherein the antenna information includes a tilt relating to thevirtual beam.
 19. The system according to claim 1, wherein the antennainformation includes a polarization relating to the virtual beam. 20.The system according to claim 1, further comprising a controllerconfigured to determine a signal strength based on a distance of acenter of the virtual beam from a center of a user beam related to thevirtual beam.